Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1150

reference: 811-tree-1
name: 1150
tree-preservation-order: undefined
811-tpo-1
uprn
address-text
point: POINT (-1.006380 50.885225)
geometry: MULTIPOLYGON (((-1.006309 50.885218,-1.006312 50.885232,-1.006322 50.885244,-1.006338 50.885255,-1.006357 50.885261,-1.006379 50.885263,-1.006401 50.885261,-1.006421 50.885255,-1.006437 50.885245,-1.006447 50.885233,-1.006451 50.885219,-1.006448 50.885205,-1.006438 50.885193,-1.006423 50.885183,-1.006403 50.885176,-1.006381 50.885174,-1.006359 50.885176,-1.006339 50.885182,-1.006323 50.885192,-1.006313 50.885204,-1.006309 50.885218)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL